Method and system for providing global multiline roaming

ABSTRACT

An approach is provided for global multiline roaming. A global roaming multiline platform provisions a communication device with a plurality of communication access numbers respectively associated with a plurality of communication service regions, wherein the plurality of communication access numbers are associated with a single subscriber identity module (SIM) of the communication device. The platform also selects a target communication access number from among the plurality of communication access numbers for relaying a communication session to or from the communication device based on a location of the communication device, a location of a called device, a location of a calling device, or a combination thereof with respect to the plurality of communication service regions.

BACKGROUND INFORMATION

Modern communication users (e.g., employees or consumers who usecellular services, mobile data services, and/or any other communicationservices) have greater mobility to travel throughout the globe. In manycases, such travel take users across communication service boundaries,thereby requiring users to make potentially complex and/or costlyarrangements to remain in communication. Historically, users who travelextensively often may have to make complex or burdensome agreements tomaintain communications. For example, users may have to enter intopotentially expensive roaming agreements or otherwise use multipledevices, Subscriber Identity Modules (SIMs), accounts, and the like tomaintain communications. As a result, service providers and devicemanufacturers face significant technical challenges to facilitatingcommunications for such global travelers. Therefore, there is a need foran intelligent global calling or other communication service solution.

BRIEF DESCRIPTION OF THE DRAWINGS

Various exemplary embodiments are illustrated by way of example, and notby way of limitation, in the figures of the accompanying drawings inwhich like reference numerals refer to similar elements and in which:

FIG. 1 is a diagram of a system capable of providing global roamingmultiline service and system (e.g., for voice, data, short messagingservices), according to one embodiment;

FIG. 2 is a diagram illustrating an example of providing global roamingmultiline service, according to one embodiment;

FIGS. 3A-B are flowcharts of the processes for providing global roamingmultiline service, according various embodiments;

FIG. 4, is a diagram of a communication network configuration forproviding global roaming multiline service, according to one embodiment;

FIG. 5 is diagram illustrating file exchanges between different entitiesof the global roaming multiline service, according to an exemplaryembodiment;

FIG. 6, is a diagram of illustrating signaling integration andinterfaces for providing global roaming multiline service, according toone embodiment;

FIG. 7 is a call flow diagram indicating a registration and signalingprocess facilitating the global roaming multiline features in theconfiguration in FIG. 4, according to one embodiment;

FIGS. 8A-B are call flow diagrams indicating, respectively, mobileoriginated call flow associated with a subscriber calling a number in ahost (e.g., foreign) network and a number in the home network, accordingto some embodiments;

FIGS. 9A-B are call flow diagrams indicating mobile terminated call flowassociated with a subscriber device roaming in a host (e.g., foreign)network calling a number in the host network and a number in the homenetwork, respectively, according to some embodiments;

FIG. 10 is a call flow diagram indicating mobile terminated call flowassociated with a subscribed device with an assigned number in a host (aforeign or international) network receiving a call on that number whilein the home network, according to one embodiment;

FIG. 11 is a call flow diagram indicating mobile terminated call flowassociated with a customer with an assigned number in a host (a foreignor international) network receiving a call on that number while roamingin a 3^(rd) party network, according to one embodiment;

FIG. 12 is a call flow diagram indicating call flow associated with amobile originated short message while the subscribed device is roamingin a host (e.g., foreign network), according to one embodiment;

FIG. 13 is a call flow diagram indicating call flow associated with amobile terminated short message sent to the local assigned number,according to one embodiment;

FIG. 14 illustrates computing hardware (e.g., computer system) uponwhich an embodiment according to the invention can be implemented,according to an exemplary embodiment.

DESCRIPTION OF THE PREFERRED EMBODIMENT

An apparatus, method, software, and system for providing intelligentglobal calling solution are described. In the following description, forthe purposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the preferred embodimentsof the invention. It is apparent, however, that the preferredembodiments may be practiced without these specific details or with anequivalent arrangement. In other instances, well-known structures anddevices are shown in block diagram form in order to avoid unnecessarilyobscuring the preferred embodiments of the invention.

In what follows, for illustration purposes, examples are given where themain scenario involves a user of a mobile device visiting countriesother his/hers and the methods and systems provided relate to theinterrelation between the networks in the visited countries and the homecountry. However, it is obvious that methods and systems introduced herecan or may be employed in other travel or roaming related scenarios.Additionally, generally, by a call (unless otherwise stated) is meant adata, voice, short message, or any other form connection establishmentin appropriate context. Various embodiments are capable of provingservices associated with voice, various forms of data and IP traffic,and short messaging and other forms of instant messaging systems.

FIG. 1 is a diagram of a system capable of providing global multilineroaming and calling, according to one embodiment. As discussed above,increased mobility and travel among consumers, employees, etc. hasresulted in potential difficulties for maintaining efficient andcost-effective communications. For example, as people travel moreinternationally, there is a need on the part of telecommunicationservice providers to provide connectivity to users when they travelabroad or outside of their home networks. Historically, serviceproviders have offered roaming services (e.g., international roamingservices) to travelers. However, compared with the same communicationservices offered on a home network, roaming services are often quitecostly (e.g., for various technological, logistical, and/or regulatoryreasons). Consequently, many customers avoid roaming services as much aspossible and resort to solutions such as using multiple SubscriberIdentity Module (SIM) cards or handsets (e.g., one for each region orservice area being visited). Maintaining multiple SIMs or handsetspotentially can be inconvenient in terms of routing calls appropriatelybetween different local numbers, paying multiple bills, transferringdata among phones or SIMs, etc.

In one example scenario, it is noted that American corporate employeesmay often travel around the world on a regular basis. These employeesalso typically spend most of their time in a handful of destinationsconducting business. Many of these employees carry multiple phones(e.g., three to four phones)—one for each country and pay multiple billsalthough they normally use those phones only when they are in thatspecific country. In other cases, some employees carry one phone as theytravel around the world, and pay typically high international roamingcharges for usage (e.g., per minute, per data allotment, per text, etc.)for the convenience.

This example scenario can be illustrated with the components of FIG. 1.For example, as shown in FIG. 1, a communication network 102 is the homenetwork to a mobile communication device 104. In one embodiment, thehome network 102 can be based on various technologies such as GlobalSystem for Mobile communications (GSM), Code Division Multiple Access(CDMA), Long-Term Evolution (LTE), etc. The device 104 is registeredwith the home network 102. The device 104 itself typically may havevarious identifiers in the network, e.g., International mobileSubscriber Identity (IMSI), Mobile Directory Number (MDN), MobileStation Integrated Services Digital Network Number (MSISDN),International Mobile Equipment Identifier (IMEI), mobile equipmentidentifier (MEID), etc. In some embodiments, a network uniqueidentification number usually (IMSI) may be stored in the device,typically in a removable SIM card or part of the Removable User IdentityModule (R-UIM).

Often a subscriber associated with the device 104 wants to visit distantregions (e.g., country, group of countries, geographical subdivisionwithin a country, etc.) that may be outside of a service area of thehome network 102. To support this, an operator of the home network 102may have bi-lateral roaming agreements with the networks 108 a-n (e.g.,service networks operating within visited regions) which amount to thedevice 104 being operable with the same identification number or accessas in home network 102. In this case, if the subscriber calls (orreceives a call from) a party with user equipment (UE) 110 a-n, thesubscriber's identity (e.g., number) associated with home network willappear on the UE 109 as, for instance, caller identificationinformation. In one embodiment, the number that will appear as calleridentification information can be the identifier of the device 104 atthe home network 102.

Generally, such a roaming service (based on roaming agreements orroaming hubs) can be quite expensive. An important reason is that theseemingly local communication between device 104 and 110 a is going tobe routed back to the home network 102 and relayed to network 108 a andthis, in fact, needs quite complicated signaling and control procedures.Another reason could be a difference in network structure andtechnologies between the host and home networks. For example, network102 could be a CDMA network while 108 a could be a GSM network (thedevice 104 may be GSM-enabled). In this case signaling and controlbetween the two networks may need an interoperability platform.Therefore, a communication and/or signaling or switching interface isemployed to couple the home network 102 and the host networks 108. Suchan interface could include e.g., international gateway, roaming hub,interoperability platform, satellite or fiber optics links, etc.).

Overall a result of such layers of network/interface and long distancesis that roaming service can be an expensive service and many people whotravel around world regularly (e.g., corporate employees) tend to avoidsuch services because of the potential expense. Instead, many of theseusers may try to purchase local SIMs or devices, while roaming and mayswap SIMs or devices for each country or region visited. When usingmultiple SIMs, for instance, users may buy bulky dual-SIM phones andleave their favorite device at home. Moreover, in such solutions onlyone number at any given point of time is generally available, and thesubscriber typically is not reachable on home number when alternate SIMsare active.

To address these problems, a system 100 of FIG. 1 introduces acapability to provision multiple local service accounts to the device104 or a single SIM associated with the devices. In one embodiment, oneof the local service accounts can be designated as the primary accountbased on the location of the device 104, while the other accounts remainactive and calls or communications directed to those accounts can berouted to the device 104. In this way, travelers may carry only onemobile device 104 and/or SIM and avoid paying potentially highinternational roaming charges while maintaining a local phone number foreach country. For example, according to some embodiments, a globalroaming multiline (GRM) platform 114 is provided which enables thedevice 104 to appear local (e.g., with access number local) to eachcountry or host network 108 visited by the subscriber. The platform 114may as well be called SIMM-R standing for Single IMSI Multiple MSISDN(Roaming)

To appear local, in this context, the device 104, e.g., registers with alocal service provider that has been previously provisioned by checkingthe devices location with a region or a host network 108 and registeringas a local device 104 with the host network 108. In one embodiment,roaming profiles with respect to the other provisioned accounts (e.g.,from the home network 102 and/or other host networks 108) can then beupdated to point to the device 104 as registered in the host network108. In one other words, the system 100, as discussed with respect tothe various embodiments described herein, provides a network-basedsolution for local device registration and roaming by intelligentlyrouting and registering among multiple provisioned networks 108available to the device 104 based on location. Further embodiments andfeatures of the global roaming multiline platform 114 are discussedbelow with respect to FIG. 2.

According to one embodiment, the device 104 may be provisioned apermanent local (access) number in each destination or region of choice(e.g., each network 108 a-n). As a result, the subscriber willdemonstrate and experience local presence to local businesspartners/peers. The convenience of a single SIM and single handset canreduce the technical and cost burdens traditionally associated withinternational roaming for communication services. For example, in oneembodiment, the subscriber can be reachable on all provisioned localnumbers at the same time. In some embodiments, the subscriber may havelower roaming rates in destinations of choice and deal with a singlebill from home operator (e.g., when the home operator have priorprovisioning and account agreements with local host networks 108).Overall the subscriber can experience seamless and improved globalconnectivity at affordable prices.

At the same time the embodiments of the invention benefit the networkcarriers or operators in various ways by, e.g., providing high-endofferings to most profitable, high average revenue per unit (ARPU)subscribers, increasing customer stickiness, acquisition of newcustomers, stimulating roaming usage, keeping subscribers within partnernetworks, leveraging existing partnerships and evaluating future ones,converting part of variable roaming revenue to assuredsubscription-based revenue, and finally maintaining industry leadershipand increase competitive advantage.

FIG. 2 is a diagram illustrating an example of providing global calling,according to one embodiment. In the example of FIG. 2, the home networkfor the mobile device 202 is a US-based network where a US access number204 is given. It is noted that the US-based home network 202 is providedas an example and not as a limitation. It is contemplated that anynetwork 202 from any region or country may be designated as a homenetwork. According to various embodiments, the subscriber may request aglobal calling service to be activated, e.g., for destinations India andChina. Upon activation of the global calling service, local accessnumbers (e.g., MDN) in India 206 and China 208 (or another othercountries or regions selected by the user) are provisioned as localaccounts with respect to the respective host networks. Such numbers mayhave been acquired through prior agreements with respective operators inthose countries or provided directly by the respective operators orservice providers themselves.

In one embodiment, provisioning includes, for instance, establishing alocal account and having a local access or network number (e.g., phonenumber) assigned to that account. For example, provisioning a localaccount enables the device 104 to register locally at the local hostnetwork (i.e., after registration the device will have a local network,identification, or access number). In this respect, the device 104 willappear as a native device within the local host network. When operatingoutside of the local host network (e.g., when receiving or making callsto devices outside of the local host network), the system 100 enables aroaming profile to update routing for all other provisioned localnumbers associated with the device, so that calls and/or communicationsdirected to any of the provisioned local numbers will be properly routedto the device at its current local host network.

In one embodiment, the system 100 can be configured so that calleridentification information displayed when making or receiving calls canshow either the number associated with the current local host network,the device's home network, or any of the other provisioned local accessnumbers (e.g., phone numbers). In one embodiment, the calleridentification number to display is based on the current location of thedevice, the location of the calling or called party, or any othercriteria configured by the user, the service operator, or a combinationthereof. It is contemplated that the platform 114 and/or the user canuse any rule, criteria, preference, etc. to specify which calleridentification number to display to which called or calling parties. Theexamples below illustrate example embodiments of global calleridentification in operation and are not intended as limitations.

As shown in FIG. 2, when the user lands in China during the first timeregistration (e.g., when the device sends a -Update Location(UL)-message to the network in China), according to various embodiments,the platform 114 (e.g., implemented as a new user profile server in someembodiments) looks at the user's custom profile and realizes that theuser is in China, it will therefore force the network components to usethe number (i.e., MDN/MSISDN) that is local to the Chinese carrier.Likewise, if the user lands in India, it may use the access number localto India. Hence in all destinations (designated service regions orcountries) the device 202 will be accessible by visited-locationcontacts via visited (local access) numbers. In some embodiments, theuser may be able to request service activation upon arrival to thedestination and the local number may be provisioned on an over-the-air(OTA) basis. For example, if a local host network detects that thedevice has not registered using a local account, the platform 114 candetermine whether the device is eligible for the global calling serviceand then send a message (e.g., a text message, voice message, emailmessage, etc.) to the user to indicate the availability of the globalcalling service and/or instructions for initiating the global callingservice. In some embodiments, the message may direct the user tospecific local carriers or operators if there are multiple operatorsavailable to choose from.

According to some embodiments, when the user is in China and calls orsends SMS messages to party with a local number (call/SMS 210), thenetwork automatically displays/presents the local MDN as the caller ID,and the user will pay the local call/SMS charges because from a networkperspective, this call/SMS will be routed completely locally instead ofbeing routed to the home country and then routed back to the visitedcountry per the current traditional roaming practice. Similarly, whenthe subscriber receives a call/SMS from a local number (call/SMS 212)the call/SMS will be treated locally at lower rates. The same situationholds in India (calls/SMSs 214 and 216).

Additionally, a local MDN/MSISDN also allows the user to keep a localpersona in the visited country. This local persona, for instance, canincrease and/or maintain a better relationship or presence with user'scustomers/partners in the visited country even when the user is notphysically in the country or region. By way of example, the local MDNcan invite more frequent calls locally, because local customers/partnerswill not pay international calling charges when they call thesubscriber. This ultimately can increase business productivity.

When the user is in a visited country, but calls or is called by a party(or sends/receives SMS to/from a party) at the home country, the callerID will now show the home country number (calls/SMSs 218 and 220).According to some embodiments, when the subscriber is in China but callsa number in India, the network will show the user's local MDN in India.

According to various embodiments, Mobile Originated call (and SMS)capability from both home and visited/local numbers will be maintained.Similarly, according to certain embodiments the device 202 may bereachable on both home and visited/local numbers concurrently. Accordingto some embodiments, the subscriber will be able to use a single primaryhandset, SIM, phone book, message inbox, etc. within a unifiedexperience in all (regions) destinations.

In some embodiments, the platform 114 may specify billing/chargingmechanisms and/or subscriptions to support the global calling service.For example, according to some embodiments, a subscriber purchasesspecific travel/roaming plans for a set of destinations. The subscribermay be provisioned in a centralized multi-line platform for roaming“local” numbers. Furthermore, the subscriber is notified of serviceactivation. Subsequently, the subscriber will be reachable through localaccess numbers available in different destinations. The subscriber maypay monthly subscription fees together with specialized rates (which canbe considerably cheaper than regular roaming) for receiving calls/SMS onthese roaming “local” numbers. All services on home number stayavailable and unaffected. Local access numbers will be available inmultiple countries to receive calls/SMS. When roaming, the local accessnumber can make calls/send SMS at specialized rates. In one embodiment,the local access numbers can be provisioned permanently or temporarilyfor a duration (e.g., a duration of a planned trip).

FIGS. 3A-B are flowcharts of the processes for providing global calling,according various embodiments. It is noted that the steps of processes300 and 320 of FIGS. 3A and 3B may be performed in any suitable order aswell as combined or separated in any suitable manner. Further, all orportions of the steps of the processes 300 and 320 may be initiated orcompleted by any of the components of the system 100, for example, bythe global roaming multiline platform 114. However, for clarity indiscussing the processes, the global roaming multiline platform 114 isreferred to as completing various steps of said processes, which may beperformed in any suitable order and where one or more of the steps maybe optional.

As shown in step 301 of FIG. 3A, the GRM 114 may receive an activationrequest for a communications device. Typically, the device may have anidentification number associated with a SIM or similar identity modules.In one embodiment, the activation request may be initiated in responseto a user's enrollment in a global calling service. In this step, thesubscriber may furthermore indicate a plurality of regions the user isplanning to visit or would like global access numbers in. In someembodiments, the platform 114 may recommend the regions or country toselect based on contextual information (e.g., roaming history, billingrecords, location traces, etc.) associated with the user. In oneembodiment, the regions are presented as individual countries. Inaddition or alternatively, a region can be defined as any geographicalarea and encompass multiple countries or a larger scale, or subdivisions(e.g., states, counties, provinces, etc.) within a country on a smallerscale.

In step 303, a plurality of access numbers (or identification numbers,e.g., MSISDN or MDN), each associated with a region to be visited, aredetermined or acquired. By way of example, access numbers can betelephone numbers (e.g., MDN) when used in the context of traditionalcellular or phone networks. In the context of other communicationnetworks (e.g., email, instant messaging, etc.) the access numbers canbe equated with user names, public profiles, or any other indicia ofidentification. For example, for a subscriber planning to visit India, alocal phone number in India is determined and assigned (e.g., based onsome agreements with local host networks). In one embodiment, theplatform 114 may be configured with a bank of available local numbersfrom which to assign. In addition or alternatively, the platform 114 mayrequest that the local host network assign or otherwise determine thelocal access number for the requesting device. In preferred embodimentsthe access number are identification numbers which allow voice, data,short messaging calls or connections.

In one embodiment, the platform 114 associates the determined accessnumbers for the selected regions with the SIM or a unique identificationnumber associated with the device. The access number may be in the formof MDN or MSIDSN. By way of example, the associated can be implementedas local accounts with the respective local host networks. In this way,when an enrolled device attempts to register in a local host network,the provisioning data for enabling local access is already configuredwith the local host network, and not information outside of the localhost network is needed to register the device for operation on the localhost network.

In step 305, the subscriber is notified of the activation of theservice. For example, the platform 114 or home network operator may senda message indicating the regions and associated local access numbers forwhich the device is configured. On activation, the user may also specifypreferences for how the global calling service is to activate including,for instance, specifying which local access numbers to make visible toothers, and/or the rules/criteria for presenting the numbers. Forexample, the user may select caller identification to present so thatthe user always appears local to called or calling parties. In othercases, may specify that only callers in a particular region (e.g.,China) will be presented with local caller identification information,while callers from all other regions will be presented with the user'shome network caller identification information. It is contemplated thatthe user and/or the service provider may set any default or personalizedconfiguration for determining how to present caller identificationinformation.

In step 307 (e.g., when the subscriber may be visiting one of theregions or may be simply trying to connect with a party in that region)a target access number associated with the region is selected from amongthe plurality of the access numbers to use as the user primary number.In one embodiment, the selection is made automatically based on theuser's location or based on which local host network the device attemptsto register from. For example, on powering up in a local host networkand initiating a registration request, the act of registering in thatlocal host network is indicative of the device's being within a physicallocation (e.g., a cell site) serviced by the local host. Accordingly, inone embodiment, the location need not be sensed or determined separatelyfrom the act of registration. In other embodiments, location informationabout device can be sensed and then registration with the appropriatedlocal host network can be initiated based on the location information.In other words, the platform 114 determines a target access number(e.g., what local access number to use for a given communication or asthe primary registered number) from among previously provided localaccess numbers to use for a device based on a location criterion. Thetarget number is then associated with the mobile device, e.g., as partof the device registration process. As discussed, the location criterionmay depend on the location of the communication device, a caller to thedevice, or a called party from the device (with respect to the pluralityof communication service regions).

In step 309 a communication session or connection may be established orrouted or relayed (or a message may be routed) according to the selectedor determined target access number. In some embodiments, subscriberinformation (e.g., caller identification information) may be presented(e.g., to the calling or called party device) based on the target accessnumber or any other of the provisioned local access numbers. In oneembodiment, the selection of a target number may affect the manner orroute in which a communication session is established and hence chargesincurred as well as the subscriber information (associated with device)which may be presented (see the example above in relation to FIG. 2).For example, when a US-based (home network in the US) device is visitingIndia and the subscriber tries to call a party with local number inIndia a target number local to India would be selected and the callwould be routed within Indian networks and the called party will bepresented local (to India) caller information. Additionally if theUS-based device receives a call from an Indian caller again the callwill not be routed to the US first and will be handled locally. In thismanner both the US-based subscriber visiting India and his or hercalling parties will incur much lower costs since there is nointernational call roaming or routing. In another scenario thesubscriber may be still in the home network but calling a party in a oneof the regions. In some embodiments the location criterion may be, e.g.,the location of the subscriber (and the device), the intended calledparty region or the region of a calling party or a combination thereof.In some embodiments an access number may be designated as the primaryaccess number based on a location criterion (e.g., to receive and answercalls from non-local access numbers).

FIG. 3B illustrates the process 320 for providing global calling,according to one embodiment. In step 321, the global roaming multilineplatform 114 may detect a request to register a communication devicewithin one of the plurality of communication service regions. This forexample can be according to standard roaming protocols and signalingschemes such as SS7 and via a roaming hub and/or an interoperabilityplatform (e.g., when a UPDATE LOCATION message is received).

In step 323, the location of the communication device can be determined(e.g., based on the signaling parameters in the SS7 messages or otherinformation available in the network). Based on this information, instep 325, an access number (or identifier) among the plurality of accessnumbers is selected and designated as a primary communication number forthe communication device while at that location. In some embodiments theoption may be given (e.g., to the subscriber) to select a specifictarget access number. Furthermore a profile associated with thesubscriber may be update. According to some embodiments a profileassociated with the device or subscriber may be updated to includedesignated target access number. This may include a roaming profile orbilling/personal (e.g., according to various levels of the CAMELstandard) or other forms of subscriber data.

In step 327, the profile may then be transferred or relayed to a networkentity (e.g., a location register) in one of the communication serviceregions (based on the determined location). These steps may beimplements as part of standard SCCP messaging such as InsertSubscription Data (ISD). Consequently the visited network (or itsrelevant entities) will have access to the subscriber's profile andaccess number(s) and as a result communication sessions to or from thedevice can be handled appropriately.

FIG. 4, is a diagram of a communication network configuration forproviding GRM (or SIMM-R), according to one embodiment. The home network402 may be (or include) a wireless (cellular or otherwise) network withtechnologies such as GSM, CDMA, LTE providing access to a mobilecomputing/communication device 404 (a phone, PDA, tablet, wearablecamera/device etc.). The mobile device 404 may also include a subscriberidentification module (SIM) 406 which may include a unique identifier(usually a number) associated with the device or the subscriber (user).The network may include one or more home location registers (HLR) 408which may obtain and register the current location of mobile deviceswhen they are within or roaming outside the network 402. The signalingand control exchanges may take places over a network 410 configured tohandle Signaling System 7 (SS7) protocol, its variants, or similarprotocols. In particular, standards such as Signaling Connection ControlPart (SCCP) may be employed to convey control messages and signals. TheSS7 network 410 may comprise of various Service switching points (SSPs),signal transfer point (STPs), and service control point (SCPs) which cancommunicate with other associated entities depicted. In particular theSS7 may include a Home Operator (HO) STP (e.g., a Verizon Wireless™ VWZSTP).

Intelligent Network (IN) or Wireless Intelligent Network (WIN)principles may be employed in various parts of the network configuration400. The operator of the network 402 and other networks in configuration400 may control various aspects of the calls between communicationentities (mobile or stationary devices or network elements, etc.)according to a variety of protocols and standards. An example of such aprotocol (standard) is Customized Applications for Mobile networksEnhanced Logic, or CAMEL. or its various phases (all of which areincluded herein by reference to documents such as 3GPP TS 02.78, 3GPP TS22.078, 3GPP TS 29.078 maintained by European TelecommunicationsStandards Institute (ETSI)).

When the mobile device 404 visits a network 412 in a different serviceregion (in this example another country) a standard roaming service maybe available. The visited network 412 typically includes one or moreMobile Switching Centers (MSC) 414 and Visitor Location Registers (VLR)416 which may operate according to various mobile communicationprotocols or standards and are employed to provide services such asroaming. The visited network may be partner visited network (FPMN) or anon-partner (in the GRM service) visited network (VPMN).

The SIM 406 inside the mobile device 404 may include a unique identifierwhich may help the network components (e.g., MSC/VLR) to identify thedevice and its home network (and its associated address or number) andthereby initiate a roaming session. Such an identifier maybe an IMSInumber. The visited network 412 and home network 402 may be coupledthrough an International Multiline Gateway and Hub (IMGH) 418. Such agateway may provide various levels of connectivity e.g., communicationchannels (e.g., voice or data), dedicated signaling channels, orchannel-associated signaling (CAS). In particular, IMGH 418 enablesexchange of SS7 messages and it may include various SSPs, STPs, and/orSCP nodes. Additionally, the IGMH 418 may include international roaminghubs where a hub operated possibly by a third party handles roamingprocedures or it may include interoperability platform where adaptationbetween different communication or messaging technology could happen(e.g., if the visited network 412 is a GSM network and the home network402 is a CDMA network, then such a platform may be employed).

The Steering For Roaming (SOR) platform 420 is a platform configured(among other functionalities) to steer communication sessions (e.g.,call, data, or SMS) for devices roaming in the visited network tofavorable roaming partner(s). For that purpose signaling schemes andCAMEL applications may be employed. In some embodiments an Over The Air(OTA) platform 424 may be available to provide over-the-air SIM ormultiple SIMs for various purposes such as roaming for voice or datae.g., General packet radio service (GPRS). SOR allows registration froma preferred network, manual mode, or QOS (quality of service) expiry.SOR platform 420 may reject UL from non-preferred network. In someembodiments the platform 420 may provide other additionalfunctionalities such as multiline functionalities.

According to some preferred embodiments a Global Roaming Multiline (GRM)(or Global Mobility Management (GMM)) platform 422 is provided tofacilitate certain global calling features disclosed earlier. In someembodiments the GRM platform 422 may be part of the SOR platform 420(in-signal mode) and in some embodiments it may be employed inmonitoring mode where it listens to exchanges signals between otherentities and reacts accordingly. This results in flexible deploymentoptions. Some embodiments may be implemented through SS7 and/or OTAintegrated application logic. In some other embodiments the GRM platform422 may include the SOR platform and some other platforms or logics suchas interoperability platforms/interfaces, SS7 STP's and other signalinginterfaces for global roaming.

In some embodiments (after registration of the device) the SOR platform420 (or a network traffic redirection platform (NTR)) performs rulescheck and sends a list of new public land mobile networks (PLMN) in anOTA message (through OTA platform 424). The salient novel functionalfeatures of Roaming MultiLine (SIMM-R/GRM) are described next.

Profile Management: Each MSISDN number that the SIMM-R subscriber has isreferred to as a profile. The original profile associated with the homeMSISDN is called primary profile, while the other profiles associatedwith the partner (foreign) MSISDN(s) are called secondary profile(s).All supplementary services like call-barring, roaming, etc. of eachprofile are separately manageable, according to some embodiments. Inpreferred embodiments, the subscribers may perform various operations tomanage their profiles. These operations are listed in the “SubscriberInitiated Operations” feature below.

Ease of Provisioning: In preferred embodiments, the SIMM-R service doesnot require the subscriber to go to operator stores and swap their SIMfor another in order to avail of the service. Subscriber can seamlesslyactivate secondary MSISDN(s) i.e. profiles on their existing SIM viaSMS/USSD. The option to avail of the service via operator stores or onoperator website is of course also available via powerful SIMM-R XMLAPIs that operator CRM, provisioning and website systems can easilyintegrate with.

Number Management: According to preferred embodiments the SIMM-R'snumber-management system saves operators the hassle of managing thelifecycle of these secondary (i.e. partner) numbers. Once home operatorpre-provisions a pool of available secondary numbers in the SIMM-Rplatform, SIMM-R automatically manages their lifecycle from Available toAllocated to De-allocated to Quarantined (a state in which a numberstays after de-allocation for an operator-configured period of timebefore becoming available again for allocation) and back to Available.

Subscriber Initiated Operations: According to preferred embodiments thesubscriber can perform several operations, some of which mayinclude—disable MT Call/MT SMS on any profile, time-band based MTactivity barring and call-forwarding control. These operations areexecuted by the subscriber as USSD commands. The format of the USSDcommands as well as the USSD string sent in response to the commands isalso operator-configurable.

According to preferred embodiments global seamless voice, SMS and dataservices are made available: (1) Receiving Calls & SMS: According tosome embodiments the subscriber can receive calls and SMS on both thenumbers at all times; (2) Making Calls & SMS: According to someembodiments a default profile is activated depending on the subscriber'slocation (See details below). Depending on which profile is currentlyactive, the receiving party of the call or the SMS will see thecorresponding CLI; (3) Data Access: According to some embodiments GRMplatform roaming ML needs to be in path of control traffic to changeprofile.

Class of Subscriber: According to preferred embodiments a Class ofSubscriber (CoS) determines available service level, and has a set ofsubscription features associated with it. In preferred embodiments theSIMM-R system allows defining various CoS for the purpose of subscriberprovisioning. When a SIMM-R subscriber is provisioned in the system, aCoS can be associated with the subscriber whereby appropriatesubscription features are enabled for this subscriber. In someembodiment the SIMM-R (GRM) system supports network-specific CoS, wherethe subscription features defined for the CoS may network/operatorcontrolled and cannot be changed by subscriber. Configuration may bedone on HPMN-VPMN-CoS basis. In some embodiments SIMM-R system alsosupports Subscriber-specific CoS, where the subscription featuresdefined for the CoS may subscriber-controlled. Configuration may be doneon HPMN-VPMN-CoS basis.

Balance check on Foreign Local number: In preferred embodiments thecustomer can check balance minutes on his or her foreign local numberthrough SMS query and free message will be delivered with balanceinformation. This feature is useful when minutes are bundled withforeign line in multiline monthly plan.

Called Line Indication (Which line was called): As a SIMM-R subscriberis reachable on any of his profiles, subscriber should be able todetermine which of their numbers (profiles) has been called by using theCalled Line Indication for the incoming call. According to preferredembodiments when a SIMM-R subscriber is called on any of his/hersecondary profiles, the secondary profile id (e.g., #n where n=1, 2, 3,etc.) is pre-pended (prefixed) to the calling number. If subscriber iscalled on their primary profile, then calling number is not modified.Flash SMS also can convey which line is called during call setup time.In some embodiments flash SMS immediately may appear on the screenwithout need to check inbox for text thus enriching user experience toget information about line which was actually called.

Incoming Call/SMS Barring: According to preferred embodiments asubscriber can selectively allow or bar all MT activity (voice call andSMS) on a given secondary profile. For example, subscriber may choose tohave only MO call/SMS capability on one profile while having both MO andMT call/SMS capability on another profile. In some embodiments thesubscriber can make this profile change using USSD. By default, MTcall/SMS are available on each profile. Time-Band Based MT ActivityBarring: According to preferred embodiments the subscriber can define atime band for each secondary profile for which all MT activities will bebarred. In some embodiments the subscriber/user can set “From time” and“To Time” in 24-hr HHMM format (e.g. 1700 to 0600).

Flexible Subscription Plan Management: According to preferredembodiments a Subscription Plan defines the various settings used togovern a subscription. The (home) operator can create multiple planswithin the SIMM-R platform. In some embodiments each subscriber can beassociated with only one Plan, but a plan can be associated with anynumber of subscribers. In some embodiments a plan may control attributeslike the subscription and renewal periods, renewal modes (auto-expiry,auto-renewal) and charging parameters (separately for subscription andrenewal)

Call Control using IN/CAMEL: According to preferred embodiments theSIMM-R system/service may have call-control on MT i.e. terminating callson the secondary (foreign) profiles via IN/CAMEL based interface withnetwork elements.

Unique Call Forwarding (Unconditional) Numbers: According to preferredembodiments the SIMM-R may support separate, unique call-forwarding FTNsfor each profile for unconditional call-forwarding and IMSI-detachscenarios. Network-based Solution: According to preferred embodimentsthe SIMM-R (GRM) solution is SIM Application and OTA independent, and italso has the capability to handle IN and CAMEL signaling. In someembodiments the SIMM-R can operate in two modes: (1) Range-based: SIMM-Ris allocated a range of secondary numbers and acts as HLR for allsecondary profiles. No secondary number provisioning is necessary in HLRof partner operator providing these secondary numbers. (2) HLRprovisioning: Operator provisions all numbers (primary and secondary) inrespective HLRs, and SIMM-R acts as MSC/VLR for secondary numbers(provisioned statically or dynamically)

SS7-based Solution: According to preferred embodiments the solution maybe built on open standards and does not utilize proprietary technologiesnor is it dependent on SIM application. In some embodiments the platformmay be a pure SS7-based solution that functions as virtual HLR, virtualVLR, virtual GMSC, virtual VMSC, virtual SMSC and virtual service nodedepending on interactions with various SS7 network elements.

Usage Record Generation: According to preferred embodiments the SIMM-Rnode is capable of generating CDRs for voice calls and Mobile TerminatedSMS. The CDRs can be used for appropriate rating, providingdiscount/rebate, billing and settlement etc. between the HPMN, FPMN andthe Multiple MSISDN subscriber. In some embodiments separate CDRs willbe generated based on the usage by different MSISDNs for MT Calls (aswell as MO calls IF MO activity needs to be routed through SIMM-R).

Number Portability Compliant: In a country where Mobile NumberPortability is supported, in preferred embodiments, it is possible forthe operator to acquire subscribers from other operators and offer themthe GRM service. In some embodiments it is also possible for subscribersto port-out the existing HPMN and FPMN numbers.

Administration and Configuration Interface: According to variousembodiments the GRM (SIMM-R) service may include intuitive and powerfulweb-based interfaces for administrative operations, and simpleconfiguration of parameters. The GUI-based Administrative Interface canbe used by the operator for provisioning Class of Service (CoS), homeand partner network details, system parameters, HLR-IMSI association,reports, etc.

High Availability: According to various embodiments, the GRM platformand service may be designed to meet high-availability requirements andthe system is usually deployed in a redundant configuration with twoVerizon Global nodes. To make Database redundant, either Oracle RAC fordata replication is used. GRM application also may also have a watchdogprocess, which oversees the state of each process and performs necessaryactions.

SNMP Support: According to preferred embodiments the system is SNMPcompliant, and may have extensive support for generating alarms forcontrol and correction activities. In addition, in some embodiments,various components of the system can be controlled through any thirdparty management console.

Activity Reporting: According to preferred embodiments the SIMM-Rsolution can support certain reports out of the box. In some embodimentsthe database may be a standard relational database (Oracle™) and canstore a variety of data at deep granularity that can be accessed togenerate special-analysis reports.

Scalable and Extensible: According to preferred embodiments the solutioncan be extended very simply and seamlessly to accommodate increases inrequirements for call volumes, signaling loads and additional partnernetworks. In some embodiments the modular and distributed architectureof the system ensures that different components can scale independentlyof each other.

Secure Access: According to preferred embodiments the system is securedfrom unauthorized access through strong authentication and authorizationschemes.

Wide Applicability: According to preferred embodiments the service canbe offered to both postpaid and prepaid subscriber categories, therebymaximizing the investment on the operator.

More functional aspects of SIMM-R (also called Global Roaming Multiline(GRM)) solution/service/system, according to some embodiments aredetailed next. Certain terms used and naming conventions are as follows:HPMN will be the subscriber's or customer's home network, which may bethe owner of the SIM card and IMSI. GMSC_H means the Gateway MSC (GMSC)of the HPMN. MSC_H is the subscriber-serving MSC of the HPMN. SMSC_H isthe SMSC of the HPMN. MSISDN_H is the MSISDN associated with primaryprofile and IMSI_H is IMSI associated with primary profile (true IMSI ofSIM). By FPMN we mean a foreign or regional partner network providingtheir network's numbers for allocation and having a roaming agreementwith HPMN. By GMSC_F we mean the GMSC of the FPMN. By MSC_F we meanSubscriber-serving MSC of FPMN. MSISDN_F is an MSISDN associated withFPMN's secondary profile. By IMSI_F we mean a (virtual) IMSI associatedwith FPMN's secondary profile. By VPMN we mean a non-partner foreignnetwork having a roaming agreement with HPMN. GMSC_V means the GMSC ofVPMN. Certain functionalities and terminology from standards such asCAMEL are employed in the description; however it is obvious that themain disclosed features are not depend upon such standards.

According to certain embodiments several deployment options andlogistics may exist. The GRM system and service may be deployed, atleast, in the following modes: (a). Outbound: i.e. deployed in HPMN;(b). Inbound, i.e. deployed in FPMN; (c). Centralized Cloud, i.e.deployed in centralized cloud-based hub (which may also double up asHPMN/FPMN); (d). Hybrid-Roaming Signaling (MAP) handled at HPMN whilecall control and translation of numbers is interfaced at Cloud.

According to some embodiments, regardless of the deployment mode, themain logistics for deploying GRM service are described below, theselogistics are generic in nature and to be adapted based on final callflows and integration topology: (a) FPMN may reserve one or moresequential block of FPMN MSISDN_F numbers to be used by HPMN forMultiple-MSISDN subscribers; (b) Deploying operator may provideMultiline with the following GTs: 1 node-specific GT for each multi-lineservice node, 1 cluster GT common across all multi-line nodes.

The common “Cluster GT” may be used by FPMN to route/initiate MAP/CAPtransactions for MT SMS and MT Call on F-MSISDN with Multiline nodes.(e.g., routing of SRI for call on MSISDN_F while in HPMN). STP/GMSC mayroute the corresponding TCAP Begin message to any Multiline Node basedon round-robin or active-standby mode, and subsequent messages in thistransaction will be done via node-specific GT assigned to that MultilineNode. This is to make sure that all messages in Transaction are throughthe same node. A message with CgPa=“Special TT” (Title Translation)mentioned below (e.g. TT=5) is to be routed to Multiline node.

In some embodiments SMSC_H may be configured to accept MO-SMS fromreserved MSISDN_F range. In yet some other embodiments, GMSC_F may beconfigured to route all messages with CdPa GT=MSISDN_F (like SRI andSRI-SM) to Multiline node. This may be done in one of 2 ways when CdpaGT=MSISDN_F: GMSC_F may modify CdPa GT to “Cluster GT,” or GMSC_F maymodify the CdPa TT to a Special TT (e.g. TT=5), and send it to GMSC ofDeploying Network.

In some embodiments, to support prefixing of CLI for MT Call onMSISDN_F, GMSC_F may be configured to support CAMEL/IN MT IDP triggeringin the following way: GMSC_F may send SRI with “suppress T-CSI asdisabled” to Multiline node, then Multiline may send “T-CSI GT asMultiline Cluster GT” in SRI-Ack, and GMSC_F to trigger MT-IDP toMultiline Node. Consequently for prefixing CLI for MT SMS, flow willremain same and no special functionality is required at GMSC_F.

In some embodiments, GMSC_F may be configured to route all E.214 (MGT)traffic of all participating HPMNs to Multiline node. This routing maybe achieved, at least, in one of two ways where CdPa=HPMN E.214 (MGT):a. GMSC_F may modify CdPa GT to “Cluster GT” (retaining NP as E.214).This mechanism may cause problems in case all Multiline nodes are downas no backup route can be defined. b. GMSC_F may modify CdPa GT to aSpecial TT (e.g. TT=5), and send it to GMSC of Deploying Network. Theabove routing may also be done as GMSC_H but it is not suggested as iteither complicates routing logic at GMSC_H or increases trafficinordinately to Multiline node.

In preferred embodiments, for MO SMS by subscriber in FPMN one of thefollowing may be configured: (a) (Preferred) SMSC_H may accept andcharge MO-SMS from MSISDN_F. No special routing is required; (b) MO-SMSmay be routed to Multiline and Multiline may relay it to SMSC_F. SMSC_Fmay be configured to have the MSISDN_F range already provisioned.Subsequently, one of the 2 routing options may be used whereCdpa=SMSC_H: (i) GMSC_F may modify CdPa TT to Special TT (e.g. TT=5),and send it to GMSC of Deploying Network; (ii) GMSC_F may modify CdPa GTto “Cluster GT”. This mechanism may cause issue in case all Multilinenodes are down as no backup route can be defined.

According to some embodiments, for prepaid subscribers the followingadditional logistics may be configured: (a) HPMN SCP may allowinteraction between MultiLine (on MultiLine node-specific GTs) and HPMNprepaid systems via CAMEL; (b) HPMN SCP may define “special” tariffs intheir prepaid systems for Roaming Multiline Subscribers to charge themdifferently than the normal Roaming subscribers. Multiline can enablethis by adding a special prefix to B-party number (for MO calls/SMS).SMS prefixing may require CAP3 support in HPMN and FPMN (but notrequired in Deploying Operator).

In some embodiments, the GPRS support for Multiline subscriber while inFPMN may be achieved in one of the following ways: (a) Multiline willnot change MSISDN in GPRS UL to MSISDN_F, i.e. all charging will occuron primary profile at regular roaming rates, and no GPRS support ispresent for any secondary (foreign) profile. No special handlingrequired; (b) MultiLine will change MSISDN in GPRS UL to MSISDN_F, andGGSN_H may be configured to allow Create PDP Request withMSISDN=MSISDN_F. All validations may be based on IMSI and not MSSIDN.This allows GPRS services to be available separately on eachprofile—primary and secondary.

In some embodiments, the HPMN Voice Mail (VM) may be configured to allowaccess for forwarded call with OCN/RDN as MSISDN_F. This is required forLCF (Late Call Forwarding) scenario where call is forwarded to VM numberwhen subscriber is in FPMN.

In preferred embodiments, provisioning may be supported via XML API overHTTP/HTTPS interface. To achieve this: (a) Deploying Operator mayprovide IP/Port on which this XML API interface will be exposed; (b)This IP/port may be opened up in Deploying Operator's firewall only forspecific Client Nodes (source IP) which will be interacting with thisinterface. Client node can be inside the Deploying Network or on variousHPMN networks (in case of centralized deployment).

In preferred embodiments, certain forms of network interface may beprovided. For example, roaming MultiLine application may be implementedwith a Signaling Gateway function having SCCP Relay capability. SCCPprotocol may be processed in the host machine. The home operator'sglobal node(s) may operate on SCCP messages. The deployment architecturemay consist of a server farm of physical Signal Gateways. Fornon-redundancy, one Signal Gateway may be sufficient. However, forredundancy and improved reliability, two gateways may be the minimumrequirement. Each Signal Gateway may be cross-connected to a GMSC/STP ofHPMN using SS7 links over E1/T1 for MAP signaling. If one link goesdown, other links in the link set can still process the SS7 messages.When both signal gateways go down, normal HLR will take over to stillsupport SIMM subscribers as normal subscribers. The number of SignalGateways, number of E1s and signaling links deployed depends on thedimensioning requirements of the operator.

In the following certain functional scenarios associated with the SIMMservice are described, according to preferred embodiment. According tovarious embodiments the SIMM-R subscriber can register (UL) and performall the below actions in HPMN, FPMN or VPMN. The signaling scenarioshandled by SIMM-R in each case are described in detail next. It isobvious that the benefits of this systems are not limited to suchscenarios.

According to preferred embodiments a registration process (e.g., the GSMUL) may be performed as follows. If the subscriber is currently in HPMNthen GRM then the PRIMARY profile is active, so MSISDN_H may be used asCLI in all MO activity. No modification is needed in subscriber's VLRprofile. If the subscriber is currently in the FPMN then SECONDARYprofile is active, so MSISDN_F may be used as CLI in all MO activity.Subscriber's VLR profile is modified accordingly to contain MSISDN_Fusing ISD. If the subscriber is currently in VPMN then PRIMARY profileis active, and MSISDN_H may be used as CLI in all MO activity. Nomodification needed in subscriber's VLR profile.

According to other embodiments, a registration process (e.g., GPRS UL)may be performed as follows. If the subscriber is currently in HPMN,then Roaming MultiLine may relay GPRS UL to HLR without SCCP CallingParty Address transformation, and does not receive any more messagesrelated to this transaction. Subscriber may receive GPRS servicenormally from HPMN i.e. PRIMARY profile is active. If the subscriber iscurrently in FPMN, then SECONDARY profile is active, so MSISDN_F may beused in all MO data activity. If the subscriber is currently in VPMNRoaming MultiLine may relay GPRS UL to HLR without SCCP Calling PartyAddress transformation, and does not receive any more messages relatedto this transaction. Subscriber receives GPRS service normally fromHPMN, i.e. PRIMARY profile is active.

According to preferred embodiments Mobile Originated (MO) calls may behandles as follows. If the subscriber is currently in HPMN, then normalGSM (or CDMA or other protocols, if applicable) process may be followed,and MSISDN_H may be sent as CLI. If the subscriber is currently in FPMN,then by default MSISDN_F may be sent as CLI. If the subscriber iscurrently in VPMN, then normal GSM process may be followed (or CDMA orother protocols applicable), and MSISDN_H may be sent as CLI.

According to preferred embodiments Mobile Originated (MO) data (GPRS)calls may be handled as follows. If the subscriber is currently in HPMN,then normal GPRS data access process is followed. If the subscriber iscurrently in FPMN, then GTP control traffic may be routed to SIMM-Rwhich may relay it to GGSN by modifying MSISDN and specialized APN. Ifthe subscriber is currently in VPMN, then normal GPRS data accessprocess may be followed.

According to preferred embodiments Mobile Terminated (MT) calls may behandled as follows. If the subscriber is currently in HPMN and the callis on MSISDN_H then Normal GSM process is followed. However, if the callis on MSISDN_F, then the call may always be routed on MSRN. However, ifcall is required to be routed on MSISDN_H (e.g. for charging purposes),then MultiLine may support this by sending primary MSISDN in Connect.User may optionally see prefixed CLI (unless “Additional Number” getsstripped off during message relay). If the subscriber is currently inFPMN and the call is on MSISDN_H, then the call may be routed to theout-roamer, i.e. this may be a regular roaming MO call, and normal GSMprocess may be followed. However, if the call is on MSISDN_F, then thecall may always be optimally routed (i.e. routed within FPMN withouttromboning through HPMN) as MultiLine sends MSRN in Connect. But if callis required to be routed through HPMN (e.g. for charging purposes), thenMultiLine may support this by sending primary MSISDN in Connect. Userwill optionally see prefixed CLI (unless “Additional Number” getsstripped off during message relay). Finally, if the subscriber iscurrently in VPMN, and the call is on MSISDN_H, then the normal process(e.g., GSM, CDMA, etc.) may be followed. However, if the call is onMSISDN_F, then the call may always be optimally routed (i.e. routeddirectly to FPMN without tromboning through HPMN) as MultiLine sendsMSRN in Connect. But if call is required to be routed through HPMN (e.g.for charging purposes), then MultiLine supports this by sending primaryMSISDN in Connect. Subscriber may optionally see prefixed CLI (unless“Additional Number” gets stripped off during message relay).

According to preferred embodiments Mobile Originated (MO) SMS may behandled as follows. If the subscriber is currently in HPMN, then normalprocess (e.g., GSM, or other applicable protocol) may be followed, andMSISDN_H may be sent as CLI. If the subscriber is currently in FPMN,then for all practical purposes, it may be assumed that the subscriberuses one of the HPMN SMSCs (SMSC_H) to send MO SMSs. Since by defaultsubscriber's VLR profile contains MSISDN_F when in FPMN, all SMSsoriginating from FPMN will have MSISDN_F as sender address. Therefore,SMSC_H may be configured to accept MO SMS messages from the specificMSISDN_F ranges. By default MSISDN_F may be sent as CLI. If thesubscriber is currently in VPMN, then normal (e.g., GSM) process may befollowed, and MSISDN_H may be sent as CLI.

According to preferred embodiments Mobile Terminated (MT) SMSs may behandled as follows. If the subscriber is currently in HPMN and a SMS issent to MSISDN_H, then normal process (e.g., GSM, or other applicableprotocol) may be followed. But if the SMS is sent to MSISDN_F, thenGMSC_F may be configured to route the MAP message Send_Routing_Info forShort Message (SRI-SM) for MSISDN-F to GMM platform 803. Multiline mayrespond with MSC as its GT (GMMM GT). The forwarded SM now comes to theGMM platform 803 and the GMM platform 803 submits it to the correct MSC.Subscriber may optionally see prefixed CLI (unless “Additional Number”gets stripped off during message relay). If the subscriber is currentlyin FPMN and the SMS is sent to MSISDN_H, then normal process (e.g., GSM,or other applicable protocol) may be followed. But if the SMS is sent toMSISDN_F, then GMSC_F may be configured to route the SRI_SM for MSISDN-Fto the GRM platform 422. GMM platform 803 may respond with MSC as its GT(GMMM GT). FSM now may come to Multiline and Multiline may submit it tothe correct MSC. Subscriber will optionally see prefixed CLI (unless“Additional Number” gets stripped off during message relay). If thesubscriber is currently in VPMN and the SMS is sent to MSISDN_H, thennormal process (e.g., GSM, or other applicable protocol) may befollowed. But if the SMS is sent to MSISDN_F, then GMSC_F may beconfigured to route SRI-SM for MSISDN-F to Roaming Multiline. Multilinemay respond with MSC as Multiline GT. FSM now may come to Multiline andMultiline may submit it to the correct MSC. The subscriber mayoptionally see prefixed CLI (unless “Additional Number” gets strippedoff during message relay). In addition to the MT SMS message itself, thesystem also transparently handles the Delivery Report and MessageWaiting functions. Net result is that the subscriber can receive SMSmessage addressed to any of the MSISDN numbers—MSISDN_H or MSISDN_F.

According to preferred embodiments unconditional call forwarding or whenIMSI is detached (e.g., from the VLR) may be handled as follows. The GRMsubscriber may need to set just one forward-to-number (FTN) for MSISDN_Hand all of the MSISDN_F that the subscriber has. The exception is FTNfor call-forwarding-unconditional (CFU), i.e. a subscriber may setseparate CFU FTNs for each of the subscriber's MSISDN_F. If thesubscriber is currently in HPMN and the call is to MSISDN_H then normalprocess (e.g., GSM, or other applicable protocol) may be followed. Butif the call is to MSISDN_F then the call may be routed to GMSC_F, whichtriggers Initial Dial Pulse (IDP) to the GRM platform 422. In the CFUcase, the GRM platform 422 sends the CFU FTN for MSISDN_F in Connect. Inthe IMSI detached case, GRM platform 422 detects IMSI-detach whensending MAP message Send_Routing_Info (SRI) on MSISDN_H, and then maysend CFU FTN for MSISDN_F in Connect. If the subscriber is currently inFPMN and the call is to MSISDN_H then the call may be forwarded to theout-roamer, i.e. this is a regular roaming MO forwarding call, andnormal process (e.g., GSM, or other applicable protocol) may befollowed. But if the call is for MSISDN_F then the call may be routed toGMSC_F, which triggers IDP to the GRM platform 422. In the CFU case, GMMplatform 422 may send CFU FTN for MSISDN_F in Connect. In theIMSI-detached case, the GRM platform 422 may detect IMSI-detached whensending SRI on MSISDN_H, and then may send CFU FTN for MSISDN_F inConnect. If the subscriber is currently in VPMN and the call is toMSISDN_H then normal process (e.g., GSM, or other applicable protocol)may be followed. But if the call is to MSISDN_F then the call may berouted to GMSC_F, which triggers IDP to the GRM platform 422. In the CFUcase, the GRM platform may send CFU FTN for MSISDN_F in Connect. In theIMSI-detached case, the GRM platform may detect IMSI-detached whensending SRI on MSISDN_H, and then may send CFU FTN for MSISDN_F inConnect.

According to preferred embodiments conditional call forwarding (whenIMSI is attached) as follows. If the subscriber is currently in HPMN andthe received call is to MSISDN_H then normal process (e.g., GSM, orother applicable protocol) may be followed. But if the call is toMSISDN_F then the call may be routed to GMSC_F, which triggers InitialDetection Point (IDP) to the GRM platform 422. The GRM platform 422 thenmay send MSRN in Connect message. Call-forwarding then may happen on FTNset for MSISDN_H directly at the serving MSC/VLR. If the subscriber iscurrently in FPMN and the received call is to MSISDN_H, then the callmay forwarded to the out-roamer i.e. this is a regular roaming MOforwarding call, and normal GSM process is followed, and normal process(e.g., GSM, or other applicable protocol) may be followed. But if thecall is MSISDN_F then the call may be routed to GMSC_F, which maytrigger IDP to the GRM platform 422, and the GRM platform 422 may sendMSRN in Connect. Call-forwarding then may happen on FTN set for MSISDN_Hdirectly at serving MSC/VLR. If the subscriber is currently in VPMN andthe received call is to MSISDN_H, then normal process (e.g., GSM, orother applicable protocol) may be followed. But if the received call isto MSISDN_F, then the call may be routed to GMSC_F, which triggers IDPto the GRM platform 422, and the GRM platform 422 may send MSRN inConnect. Call-forwarding then may happen on FTN set for MSISDN_Hdirectly at serving MSC/VLR.

Certain billing considerations in relation to the GRM service accordingto preferred embodiments are as follows. FIG. 5 illustrates related fileexchanges between various entities according an exemplary embodiment.The Global Roaming Multiline (i.e. SIMM-R) solution is a “single” IMSIsolution. This means that the FPMN 501 always sees the primary IMSI(IMSI_H) of the roamer, whatever MSISDN is being used. The key billingconsiderations may be as follows for post-paid subscribers: (a) MO Callsmay be charged via transfer account procedure (TAP) file generated byVPMN 503/FPMN 501; (b) MT Calls to F-MSISDN may be charged via GRMplatform 507 CDR files. MT TAP records can be discarded or used foradditional charging; (c) CF Calls may be charged via a combination of MOand MT call charging; (d) For SMS MO when subscriber is in FPMN 501 twooptions may be: (1) charging via TAP file generated by VPMN/FPMN. HPMNSMSC 505 CDRs should be discarded for F_MSISDNs when subscriber in FPMN;or (2) charging via SMSC CDRs. In this case SMSC should know the mappingbetween H_MSISDN and F_MSISDN; (e) SMS MT to F_MSISDN may not becharged; (f) Data (GPRS) when subscriber is in FPMN/VPMN, two optionsmay be: (1) charging via TAP file generated by VPMN/FPMN; (2) chargingvia GGSN CDRs. In this case, data sessions when subscriber is registeredin FPMN will include MSISDN_F. Thus, home charging system should beaware of this and be able to process it accordingly.

In some embodiments for GRM subscribers, transfer account procedure(TAP) files exchanged between FPMN 501 and HPMN 505 may be split basedon the home IMSI so subscribers may be charged at preferential rates.The IMSI split may be done in the home mediation system 507 withoutinvolving the default call handling (DCH). In this case, no differentInter Operator Tariffs (IOT) may be applied for those subscribers,meaning GRM traffic would be managed in the same way than regularroaming traffic. In some embodiments if DCH is involved, a differenttreatment for TAP files generated by GRM subscribers may be applied, notfollowing the same path than those TAP files corresponding to regularroamers. HPMN 505 and FPMN 501 may reach an agreement based on thenumber of GRM subscribers, excluding GRM traffic from regular roamingrelationship. In some embodiments the TAP files exchanged between anyVPMN 503 and HPMN 505 may remain the same without a change in thebilling or processes.

According to various embodiments certain administrative and provisioninginterfaces are as follows. The operator, for performing systemadministration of system parameters, GT mapping and pool management,viewing system reports, etc. can use SIMM product's GUI-basedAdministrative Interface. Provisioning Interface is meant to enroll asubscriber in the GRM system. The same interface may also be used forremoving the subscriber or modifying the subscription details of asubscriber in the GRM system. GRM service supports provisioning using aflat file containing provisioning details in comma-separated-valueformat. Provisioning process may be configured to run at predefined timeintervals (say 10 minutes). The GRM application treats all theprovisioning data updates for a subscriber as a single transaction. Ifone of the operations fails, all amendments are reverted and subscriberdata brought to a sanity status. Also, if any provisioning errorshappen, the system creates failed records with the input data file andan error text explaining the reason for failure in comma-separated-valueformat.

According to some embodiments system reports may be generated. The GRMservice may be configured to generate predefined reports that helpmobile operator gauge the utility of the service. Key business reportsthat are generated from the system are as follows: (a). Service UptakeReport; (b). Call (Voice) Usage Report; (c). SMS Usage Report. Inaddition to these reports, several operational statistics may berecorded and available for analysis.

According to some embodiment system monitoring may be implemented. Inparticular, the GRM product supports SNMP based alarm generation forreal time monitoring and control, under standardized Operations &Maintenance (O&M) procedures. The system extensively logs all thecritical events across various components and generates subsequentalarms. The current version is compliant to SNMP version 1. Some exampleSNMP statistics, alarms and controls include: (1). Current number of MAPtransactions and ISUP calls. Total number of these transactions perhour; (2). Critical alert trap when log file cannot be opened orcreated; (3). Critical alert trap when the ISUP signaling link betweenGRM platform and GMSC goes down; (4) Critical alert on databaseconnection down.

FIG. 6 illustrates signaling integration architecture between the homeand host (or partner) networks, according to some embodiments. Accordingto these embodiments signal exchanges between home network 601 andvisited (or partner) network 603 may happen through a multiline hubplatform 605. In some embodiments the platform 605 may be operated by athird party. In other embodiments the multiline hub 605 may be deployedon a global cloud platform and controlled by the home operator.

Further details on functions performed by the platform 605 will be givenbelow. The platform 605 in some embodiments may support both SS7 andSIGTRAN protocols. SIGTRAN is a protocol designed to enable SS7 signalsto be exchanged over IP networks and connections which are cheaper toemploy. Document RFC 2719 tilted Framework Architecture for SignalingTransport describes the SIGTRAN protocol all of whose contents isincluded here by references.

According to one embodiment STP 607 and 609 route messages throughmultiline hub platform 701. STP 705 may route all messages (e.g.,SS7/SIGTRAN or SMS) with reserved Global Titles (GTs) to the MultilineHub Platform 605 (e.g., a Globetouch™ platform). STP 605 may furtherroute all messages with local reserved number ranges. In someembodiments WIN triggers may be enabled for multiline customers anddefined SCP control towards the multiline hub platform 605 for real timecall control. Home network may route all the messages for multilineE.164 address to multiline client node which does MAP signalingtranslation before sending message to FPMN/SCCP carrier.

According to various embodiments the STP 609 in the partner or hostnetwork may route messages of virtual GTs to multiline hub platform 605.The STP 609 may also route reserved MSISDNs (E.164) traffic to themultiengine hub platform 605. The STP 609 may also optionally establishvoice trunks/SIP control with the multiline hub 605 for handling voicetraffic. In some embodiments CAMEL SSN may be enable for the multilinehub platform 605 so as to route CAMEL triggers to the platform 605 forreal time call control. In some other embodiments the partner network(or the STP 609) may route all the signaling for multiline GTs as wellas reserved number ranges to the multiline hub 605, wherein themultiline hub may be deployed on a global cloud platform.

FIG. 7 illustrates provision and registration processes and call flowsin a foreign partner network according to some embodiments. TheProvisioning platform 701 may include a database containing customer'sprofiles. The provision platform may also be a generic platform or aMobile Telephony Activation System (MTAS) database such as VerizonWireless™ MTAS.

In some embodiments, the Home Registration and Authentication (HRA)platform 703 may include certain location databases, e.g., homeoperators HLR, a global interface or interoperability platform (GSM andCDMA interoperability) and the related HLR such the one maintained bySyniverse™. The HRA platform 703 may further include home operatorsauthentication center. It is obvious that different exemplary componentsmentioned can be arranged in various way and with possibly differentcomponents but similar functionalities. The Over-The-Air (OTA) platformwhich could be cloud-based SIM provision platform is mainly for OTAprovisioning purposes e.g., while customer in foreign counter wants tosetup the service. In some embodiments certain functionalities relatedperformed by other entities (provisioning) in normal scenario may beperformed by the OTA 705 in obvious way, thus in what follows thespecific steps that may be performed by the OTA platform 705 will not bediscussed.

Global Mobility Management platform 707 is a platform which may includehome operator's global/international STP(s), the operator's SORplatform, the operator's global mobility management services(bookkeeping), and global multiline node(s). The Global Multiline Hubplatform (GMH) 709 is a global platform which facilitates signaling andnumber translation/management between. In some embodiments it mayinclude or facilitate certain clearinghouse/billing functionalities. Insome embodiments the GMH platform may include a number management module709 a, a global hub 709 b (to interface with various carriers andoperators), a service control point (SCP) 709 c. The VPMN 711schematically shows a visited partner network (e.g., a FPMN) or relatedSGSN/VLR.

Upon customer's request for activation a global multiline roamingservice with possibly several to-be-visited foreign countries orregions. The provisioning platform 701 may create a class of subscriber(COS) with multiline subscription and number mapping. Subsequently theProvisioning platform 701 may send a Add_Subscription message 721 toGlobal Mobility Management (GMM) platform 703.

The GMM platform 703 then may relay the Add_Subscription message to theGlobal Multiline Hub (GMH) 709 (or to its subplatform Number Managementplatform 709 a). This may happen over IP or over a propitiatory SS7network or the likes. The provisioning platform 701 may also sendAdd_Subscription 725 to the Home Registration and Authentication (HRA)platform 703. Upon completion of add subscription process a permanentnumber mapping associated with subscription of service is created andthe GMR service is activated and ready.

After activation of the GMR service, the customer may visit a regionassociated with a partner network (e.g., US-based customer who hasactivated the service may visit Hong Kong wherein a local partner partyor network in operation). Upon arrival the customer may turn on his orher communication device or my simply enter the region under coverage bythe partner. The communication device then initiates anauthentication/registration process according to standard GSM, CDMA,GPRS, etc. protocols with partner network. Subsequently, the VPMN 711(e.g., the SSGN/VLR therein) may send a Send_Authentication_Info message731 including the IMSI of the communication device to the GMM platform703. The GMM platform 707 then may relay the Send_Authentication_Infomessage to the HRA platform 703 (message 733). The authentication centerwithin the RA platform 703, may then respond with aSend_Authentication_Info_Response message 735 to the GMM platform 707.The message 735 may include certain authentication keys or token tofacilitate the authentication process. For example, in certainembodiments standard authentication quadruplets or quintuplets may beincluded in the message. Subsequently the GMM platform 707 may relay theSend_Authentication_Info_Response to VPMN 711 (message 737).

Subsequently the VPMN 711 may authenticate the customer's communicationdevice and then initiate an Update Location (UL) or registrationprocess. Thereby the VPMN 711 may send a UL message 739 including theIMSI of the device to the GMM platform 707. Then the GMM platform 707may relay the UL message to the HRA platform 703 (message 741). Inpreferred embodiments the GMM platform may set the SCCP CgPa as the SORGT with MSC and VLR address as the GMH's GT address (e.g., the SCPaddress therein). In some embodiments, if a UL message is received for amultiline customer then the GMM platform 707 (or the SOR platform withinit) may insert itself into relay path for Insert_Subscriber_Data (ISD)message. It may change the SCCP Calling Address to its GT. There isflexibility to choose an alternate GT for MAP VLR/MSC address. Thisgives flexibility to keep multiline MAP signaling node at in-networknode (e.g., within the GMM platform 707) or as part of the GMH platform709 (e.g., Globetouch™ platform).

Subsequently the HRA platform 703 may respond with anInser_Subscriber_Data (ISD) message 743 which may include the customer'sprofile and the home MSISDN. Subsequently, the GMM platform 707negotiates with the GMH platform 709 and the Number Management platform709 a to resolve the current location of the device (Publish_Locationmessage 745 which may contain the location information about thedevice). Subsequently the GMM platform 707 may modify the ISD message bychanging the MSISDN to the local (or foreign) F_MSISDN at the visitedregion (e.g., Hong Kong or another country visited). The GMM platform707 may also insert a CAMEL Application Part (CAP) O-CSI profile forfurther call control. The modified ISD message 747 is then transmittedto the VPMN 711. Therefore, if the device has local MSISDN (MDN), thenthe MSIDSN is modified to the local in the roaming country. Subsequentlythe VPMN 711 responds back with the message Insert_Subscriber_DATA_RESP749 to the GMM 707, which is relayed to the RA platform 703 (message751). The HRA platform 703 subsequently sends anUpdate_Location_Acknowledge message 753 to the GMM platform 707, whichis then relayed to the VPMN 711 (message 755).

In the above for simplicity, GSM and data GPRS UL's are not shownseparately. The GRM solution provided applies similarly to voice (andSMS) as well as data. This can be expanded along with message flowbetween international SCCP carriers as part of detailed integration callflows. It is apparent that certain functionalities from the CAMELprotocol have been employed. In general limited functionality of CAMEL(or similar protocols) is needed, thus deployment will not becomplicated for a partner network who may not employ such a protocol.

FIG. 9A illustrates call flows associated with a mobile originated MOvoice call when the customer roaming in a visited region (or country,e.g., Hong Kong) calls a local number in that region (or country),according to an exemplary embodiment. In certain embodiments the localnumber may be even any number defined under the visited region. Forexample it could be a number in a third country, e.g., the US-basedcustomer visiting Hong Kong may call number in China, in which case thelocal Hong Kong CLI associated with the customer may be displayed on thereceiving party's device.

FIG. 8A illustrates a call flow diagram associated with the scenariowhere after registration/UL) a customer roaming in a partner network(e.g., a US-based customer in a network in Honk Kong) makes a call to aparty in the same network (e.g., in the HK network) or a party in acountry number defined under the partner network number region (e.g.,China in the case of Hong Kong). The customer may be given the option toselect one or more such countries/numbers. Therefore, the customernumber A#=MSISDN_F may be a Hong Kong number and the called number maybe B#=NUMBER_F a Hong Kong or China number (possibly with a prefix). TheMO CALL Initial Address Message (JAM) JAM (A#=MSISDN_F AND B#=NUMBER_F)(message 801) with optionally a prefix may be received from the deviceat the VPMN partner 711. Subsequently VPMN 711 sends the Initial DPDial/Dialed Pulse (IDP) IDP (H_MSISDN, CgPa=A#, CdPa=B#) to the SCPplatform 709 c of the GMH platform 709 (message 803). Subsequently theGMH platform 709 may analyze the calling party number (CgPa), VPMN, thecalled number (CdPa) and may take a decision to modify the Calling LineIdentification (CLI) or not. In this case, CLI is not modified. Also,depending upon integration architecture with the partner VPMN, B# may bemodified by adding a prefix to facilitate billing mediation to filterout selective CDRs. Subsequently the SCP sends a CAP Request ReportBSCSM (RRB)+Continue/Connect (Notify & Continue) message to the VPMN 711(message 805). The rest of call establishment may follow as normal(arrow 807). When the call is established the VPMN may send CAP EventReport Basic Call State Model (BCSM, ERB) ERB O-ANS (message 809).Similarly the VPMN also may send a disconnect message ERB O-Disc(message 811) when the call is disconnected. In some embodiments, callmay be interfaced by multiline CAMEL SCP node and local CLI will bedisplayed as caller number. Additionally CDR may be generated atMultiline SCP 709 c as well as FPMN/MSC. The FPMN may filter the CDRbased on Multiline SCP 709 c address and TAP file may be exchangedthrough the GMM platform 705. CAMEL parameters suppression may berequired in the TAP Record if home operator billing system doesn'tprocess CAMEL parameters received in the TAP file.

FIG. 8B illustrates a MO Call from the customer to a number in thecustomer's home network (e.g., the US-based customer above may call a USnumber or a to a 3rd country number defined under the home network'sregion by the customer, e.g., Canada. In this case CLI is modified toHome CLI and US number is displayed. The customer with local number(A#=MSISDN_F) may call a number B#=NUMBER_H in home network or under theregion defined by the home network number (possibly with a prefix). TheMO Call JAM (A#=MSISDN_F and B#=NUMBER_H) (message 821) with optionallya prefix may be received from the device at the VPMN partner 711.Subsequently VPMN 711 may send the Initial DP Dial Point (IDP)IDP(MSISDN_H,CgPa=A#, CdPa=B#) to the SCP platform 709 c of the GMHplatform 709 (message 803). Subsequently the GMH platform 709 similar tothe previous case analyzes the calling party number (CgPa), VPMNSGSN/VLR, the called number (CdPa) and may take a decision to modify theCLI or not. In this case, however, CLI is modified using Generic_Addressfield in the CAP CONNECT message. Also, depending upon integrationarchitecture with the partner VPMN, B# may be modified by adding aprefix to facilitate billing mediation to filter out selective CDRs.Call may be finally terminated on non-prefix number. The SCP 709 c maysend CAP message RRB+CONNECT(Generic_Address=MSISDN_F,Destination_Routing Address=NUMBER_H) to VPMN. The rest of the call flowmay be exactly similar to the previous example, 827 indicates standardcall flow and messages 829 and 831 indicate ERB O-ANS and ERB O-DISCmessages, respectively.

FIG. 9A illustrates the call flow associated with a MT call when thecustomer is roaming in a partner network, receiving call on the number.The example could be the US-based customer with roaming in Hong Kongwith US number B#=MSISDN_H receiving a call from a party with US orCanada number. By way of example a home CDMA network is shown withprotocol ANSI 41 (or IS 41). However, it is obvious that essentiallysimilar arrangements and protocols may be employed for other homenetworks such as GSM, LTE, etc. The CDMA MSC 901 and CDMA HLR 903 may beconsidered as part of the HRA platform 703 or separately. The I-HLR 905may be interface or interoperability/inter-standard HLR or gateway whichmay facilitate interconnectivity between CDMA and other protocols suchas GSM or 3Gpp. The I-HLR 905 in some embodiments may be included in theGMM platform 707. In some embodiments the I-HLR 905 platform may beoperated by a third party.

The (voice) MT call to MSISDN_H number from a party in the home networkor region associated with it with number A# may be received at the CDMAMSC 901. The CDMA MSC 901 sends the ANSI41 message LOCATION_REQUEST(message 913) with called number (B#=MSISDN_H) to the CDMA HLR 903. Thenthe CDMA HLR 903 sends an ANSI41 ROUTE_REQUEST (B#=MSISDN_H) request tothe I-HLR (message 915). Subsequently, the I-HLR 905 sends the MAPmessage PROVIDE_ROAMING_NUMBER(IMSI) on the hub serving MSC/VLR addressto the GMM platform 707 with the IMSI number of the called device(message 917). Then the GMM platform 707 relays the messagePROVIDE_ROAMING_NUMBER(IMSI) to the VPMN 711 (message 919). In returnthe VPMN 711 responds with the MAP message PROVIDE_ROAMING_NUMBERRESULT(MSRN_F) where MSRN_F is the MSRN of the roaming device in thevisited/or partner network VPMN 711 to the GMM 707 (message 921).Subsequently, the GMM platform 707 may send the LOCAL_DID_REQUEST(A#,B#=MSRN, POP ID) over IP or proprietary FSM over SS7 to the hub 709 b(message 921 a) asking for local Direct Inward Dialing (DID) number andPOP ID is the point of presence ID. Optionally, the international MSRNcan be modified to a local home DID (e.g., a local US DID) to collectcalls through the GMH's preferred carrier and re-routed to final MSRN_Fnumber. Then the hub 709 b may send back LOCAL_DID Response(local DID)over IP or proprietary FSM over SS7 to the GMM 707 (message 921 b).Subsequently the GMM 707 may send the MAP message PROVIDE_ROAMING_NUMBERRESULT(local DID/MSRN_F) to I-HLR 905 (message 923 which is the resultof message 917). Then the I-HLR sends the MAP messageINSERRT_SUBSCRIBER_DATA (IMSI, LCF FTN) on GMH's GT to the GMM platform707 (message 925). Then the GMM sends a stand-alone (SA) MAPSA_ISD(IMSI, LCF FTN) on VPMN MSC/VLR to the VPMN 711 (message 927).Then the VPMN 711 responds back with SA-ISD_Ack (message 929). Then theGMM 707 relays the SA_ISD_Ack to the I-HLR 905 (message 931). Then theI-HLR responds back with MAP SA_ISD_END to GMM platform 707 (message933) which will be relayed to the VPMN 711 (message 935). On the otherhand, the I-HLR sends the ANSI41 message Route_Req_Result(GMH_DID)(i.e., with GMH_DID as the MSRN) to CDMA-HLR 903 (message 937). Then theCDMA-HLR 903 relays the ANSI41 message LOCATION_REQUEST_RESAULT(GMH_DID)to the CDMA MSC 901 (message 939). Thus the MT call is terminated on theGMH MSRN (message 943) and the voice call (945) on GMH 709 MSRNcollected by GMH through POP (Point Of Presence). Also at the same timethe voice call (947) is terminated on the MSRN_F after translation bythe GMH 709. Then roamer is paged and call is terminated (949). It isevident that the GMM platform or a multiline node may relay themessage(s) from I-HLR (or its component within e.g., Syniverse™ HLR) toGPMN VLR and vice-versa. The MT call may be routed to original MSRN orin some embodiments via a global hub 709 b (e.g., Verizon™ Global Hub)through its preferred carrier.

FIG. 10 B illustrates a MT call flow diagram associated with a customerroaming in a partner network with assigned B#=MSISDN_F and receivingcall from a party with a number A# in the partner network or a regiondefined under the partner HK, according to some embodiments. For examplea US based customer in roaming in Hong Kong may receive a call fromparty with Hong Kong number or China number (call 951). The VPMN 711 maysend the MAP message SEND_ROUTING_INFO (MSISDN_F) to the hub 709 b(message 953). In return the hub 709 b may respond with MAP messageSEND_ROUTING_INFO_RESULT(T-CSI, LOC INFO, O-CSI) giving informationabout the called device (message 955). Then the VPMN may send the CAPmessage IDP_12(IMSI, A#, B#) to the hub 709 (message 957). In return thehub 709 b may respond back with the CAP message RRB+CONNECT(DRA=GMH_DID), message 959. Subsequently call may be terminated on theGMH_DID through the GMH (or the hub 709 b)'s preferred voice carrier(call 961). Thus the MT call is router on GT DID (call 963). The voicecall is routed on home MSISDN/MDN (call 965). Subsequently the CDMS MSC901 may send the ANSI41 message LOCATION_REQUEST (B#=MSISDN_H) to theCDMA HLR 903 (message 967), which in turn relays the message ANSI41ROUTE_REQUEST (B#=MSISDN_H) to the I-HLR 905 (message 969). The I-HLR905 then may send the GMM platform 707 the MAP messagePROVIDE_ROAMING_NUMBER(IMSI, GMSC_ADDRESS) on hub serving MSC/VLRaddress (message 971). Then the GMM platform may send the MAP messagePROVIDE_ROAMING_NUMBER (IMSI, GMSC_ADDRESS) to the VPMN 711 (message973). The VPMN 11 then responds with the MAP messagePROVIDE_ROAMING_NUMBER_RESULT(MSRN_F) conveying the associated localMSRN_F (message 973). According to some embodiment the FPMN GMSC isconfigured to route SRI request to Multiline Hub 709 b, which returnshome MDN as MSRN or local DID. Thus the call is routed directly to homeMDN or via the GMH platform through its preferred carrier and afterwardsit follows the same call path as if call is made to the home number(MDN).

Subsequently, the GMM platform 707 may send the LOCAL_DID_REQUEST(A#,B#=MSRN, POP ID) over IP or proprietary FSM over SS7 to the hub 709 b(message 975 a) asking for local Direct Inward Dialing (DID) number andPOP ID is the point of presence ID. Optionally, the international MSRNcan be modified to a local home DID (e.g., a local US DID) to collectcalls through the GMH's preferred carrier and re-routed to final MSRN_Fnumber. Then the hub 709 b may send back LOCAL_DID_Response(local DID)over IP or proprietary FSM over SS7 to the GMM 707 (message 975 b).Subsequently the GMM 707 may send the MAP message PROVIDE_ROAMING_NUMBERRESULT(local DID/MSRN_F) to I-HLR 905 (message 975). Then the I-HLRsends the MAP message INSERRT_SUBSRIBER_DATA (IMSI, LCF FTN) on GMH's GTto the GMM platform 707 (message 977). Then the GMM sends a stand-alone(SA) MAP SA_ISD(IMSI, LCF FTN) on VPMN MSC/VLR to the VPMN 711 (message979). Then the VPMN 711 responds back with SA-ISD_Ack (message 981).Then the GMM 707 relays the SA_ISD_Ack to the I-HLR 905 (message 983).Then the I-HLR responds back with MAP SA_ISD_END to GMM platform 707(message 985) which will be relayed to the VPMN 711 (message 987). Onthe other hand, the I-HLR sends the ANSI41 message Route_Req_Result(GMH_DID) (i.e., with GMH_DID as the MSRN) to CDMA-HLR 903 (message989). Then the CDMA-HLR 903 relays the ANSI41 messageLOCATION_REQUEST_RESAULT(GMH_DID) to the CDMA MSC 901 (message 991).Thus the MT call is terminated on the GMH MSRN (message 993) and thevoice call (995) on GMH 709 MSRN collected by GMH through POP (Point OfPresence). In one embodiment the voice call may be placed on GlobeTouch™MSRN collected by GlobeTouch™ through PoP (point of presence). Also atthe same time the voice call (997) is terminated on the MSRN_F aftertranslation by the GMH 709 or the multiline hub 709 b. Then roamer ispaged and call is terminated (999).

FIG. 10 illustrates a MT call when the customer is at home network andreceiving call on the number B#=MSISDN_F local to a partner network froma number A# in the partner network, according to some embodiments. Animportant example is when family and business partners of the customer(e.g., a US customer) in a third country (e.g., Hong Kong) would like tocall the customer but desire to avoid expensive international calls.Most of the components in this figure are as in FIG. 9A except for theCDMA MSC 901 in FIG. 9A is replaced with two CDMA MSC's 1001 and 1003(e.g., to indicate a practical roaming scenario within the homenetwork).

The MT call is made from #A to the customer on the local MSISDN_F (call1011). Then the VPMN sends the MAP message SEND_ROUTING_INFO (MSISDN_F)to the (multiline) hub 709 b (message 1013). The hub in return respondswith the MAP message SEND_ROUTING_INFO_RESULT(T-CSI, LOC INFO, O-CSI)giving information about the called device (message 1015). Then the VPMNsends the CAP message IDP_12(IMSI, A#, B#) back (message 1017).Subsequently the hub 709 b responds with the CAP message RRB+CONNECT(DRA=Hub_DID) (message 1019) and the MT call will be routed on GT DID(message 1021). Then the voice call is terminated on Hub_DID the hub'spreferred voice carrier (message 1023). The other side of the voice callis routed on home (e.g., USA) MSISDN/MDN (message 1025). SubsequentlyCDMA MSC 1001 sends the ANSI41 LOC_REQ (B#=MSIDSN_H) to the CDMA HLR 903(message 1027). Then the CDMA HLR 903 sends the ANSI41 ROUTE REQ(B#=MSISDN_H) to the other CDMS MSC 1003 (message 1029). In this casethe CDMA MSC 1003 is serving the called device and send the ANSI41message ROUTE_REQ_RESULT (TLDN:MSRN) to the CDMA HLR (message 1031). TheCDMA HLR 903 send the ANSI41 message LOCREQ_RESULT (TLDN:MSRN) to theCDMA MSC 1001 (message 1033) and also terminated the call on the MSC1003 serving the customer (message 1035). On the other side the VPMNsends the CAP message ERB (T-ANS, T-DISC) to hub upon disconnection ofthe call (message 1035 a). In preferred embodiments the call is routedthrough the hub 709 b's or the GMH's platform core network the homeoperator's network (e.g., through GlobeTouch™'s core network toVerizon™'s network in the USA). In preferred embodiments FPMN GMSC isconfigured to route SRI request to GMH 709 or hub 709 b, which returnshome MDN as MSRN or global nodes or gateways/hubs of the home networklocal DID (e.g., Verizon™ Global local DID). The MT call is routeddirectly to Home MDN or via home network's global hub through itspreferred carrier and afterwards it follows the same call path as ifcall is made to the home number (MDN).

FIG. 11 illustrates call flow associated with MT call to the customer ofthe GRM service when the roaming in 3rd country and receiving call onthe number B#=MSISDN_F in a partner network from a party with number A#in the partner network. An example could be the US based customerroaming in France (a VPMN other than FPMN) and receiving a call on thecustomer's Hong Kong number. In this case the call is routed through isrouted through the hub 709 b to the home operator's network and fromthere is routed again to France.

The MT call is made from #A to the customer on the local MSISDN_F (call1111). The VPMN 707 sends the MAP SEND_ROUTING_INFO (MSISDN_F) to thehub 709 b (message 1113). Then the hub 709 b sends the MAP messageSEND_ROUTING_INFO_RESULT(T-CSI, LOC INFO, O-CSI) back to the VPMN 711(message 1115). Then the VPMN responds back with the CAP messageIDP_12(IMSI, A#, B#) (message 1117). The hub sends the CAP messageRRB+CONNECT (DRA=hub_DID) to the VPMN (message 1119). Subsequently theMT call is routed on GT DID (1121). The voice call is terminated on hubDID hub's voice carrier (1123).

On the other hand the voice call is routed on home MSISDN/MDN (1125).The CDMA MSC 901 sends the ANSI41 message LOC_REQ(B#=MSISDN_H) to theCDMA HLS 903 (message 1129). The CDMA HLR in turn relays the message tothe I-HLR for interoperability translation. Then the I-HLR sends the MAPmessage PROVIDE_ROAMING_NUMBER (IMSI, GMSC) to the 3^(rd) party MSC/VLR1101 (message 1131). The 3^(rd) party MSC/VLR responds back with the MAPmessage PROVIDE_ROAMING_NUMBER_RESULT (MSRN) returning the MSRN of thedevice (message 1133). Subsequently the I-HLR sends the ANSI41 messageROUTE_REQ_RESULT (TLDN:MSRN) to the CDMA HLR 903 (message 1135). Thenthe CDMA HLR send the ANSI41 message LOC_REQ_RESULT (TLDN: MSRN) to theCDMA MSC 901 (message 1137). The MT call is terminated on MSC servingthe customer (message 1139) and when the call disconnected the VPMN 711sends the CAP message ERB (T-ANS, T-DISC) (message 1139 a). It isobvious that similar considerations as those in the previous scenariosmay apply.

FIG. 12 illustrates call flow associated with MO SM sent by the customerroaming in the partner network VPMN to a party with number in the homenetwork. HOME SMSC 1201 is the home operator's SMS server. In thisscenario the SM will be submitted to the Home SMSC 1201 afteroriginating address (i.e., CLI) modification to home number.

Upon receiving the SM the VPMN sends (forwards) a MAP message MO FWD SMto the I-HLR 905 (message 1211). The parameters of the message may be:SCCP CdPA:SMSC-GT (E.164), SCCP CgPA: MSC-V (E.164),MAP_LEVEL_PARAMETERS: IMSI: IMSI, SM-RP-DA: SMSC, SM-RP-OA: MSISDN_F,SM-RP-UI: RECEIVER'S MSISDN & MESSAGE TEXT. If the message it isreceived for originating address belonging to multiline COS then theI-HLR 905 routes the MO FWD SM 1211 to the multiline node within GMMplatform 707 (message 1213). The parameters of the MO FWD SM message1213 may be: SCCP CdPa: SMSC-GT (E.164), SCCP CgPA: I-HLR (E.164),MAP_LEVEL_PARAMETERS: IMSI: IMSI, SM-RP-DA:SMSC, SM-RP-OA: MSISDN_F,SM-RP-UI: RECEIVER'S MSISDN & MESSAGE TEXT. Then multiline node modifiesSM-RP-OA to MSISDN_H (the subscriber's number at home network) sincehome SMSC may not authorize SM from the local number at the partnernetwork (i.e., MSISDN_F) and relays MAP_MO_FWD_SM message 1213 to I-HLR(message 1215). The parameters of the message 1215 may be: SCCP CdPA:I-HLR (E.164), SCCP CgPA: multiline (E.164), MAP_LEVEL_PARAMETERS: IMSI:IMSI, SM-RP-DA: SMSC, SM-RP-OA: SENDER' MSISDN_H, SM-RP-UI: RECEIVER'SMSISDN & MESSAGE_TEXT. Subsequently the I-HLR sends the point to pointshort message MAP Short_Msg_MO_PtoP (message 1217) to the (CDMA) HomeSMSC 1201. The CDMA SMSC 1201 delivers the message to the recipient andin turn sends the acknowledge message Short_Msg_MO_PtoP_Ack to I-HLR(message 1219). The I-HLR then sends the MAP MO_FWD_MO_SM_Ack withCgPA:I-HLR and CdPA: multiline, to the multiline node within the GMMplatform 707 (message 1221) which relays back the message to the I-HLR(message 1223). The parameters of the message 1223 are CgPA:multiline,CdPa:I-HLR. The I-HLR then finally relays the acknowledgement message tothe VPMN 711 (message 1225) with parameters: CdPa:I-HLR SMSC GT,CdPa:V-MSC.

FIG. 13 illustrates the call flow associated with the MT SM send to thenumber local to a partner network (MSISDN_F). The InterWorking Function(IWF)-SMSC and partner GMSC 1301 indicates the point where the SM may bereceived initially. The SMPP GW 1303 is a short message peer to peergateway (SMPP) and V-MSC 1305 is MSC of the partner network. The examplecould be a US-based customer having a Hong Kong number through the GRMservice and receiving SMS on that number.

According to some embodiments the FPMN GMSC in 1031 may be setup toroute all the request for reserved MSISDN range to home operator'sglobal nodes, SRI-SM request from any IWF-SMSC will be routed to themultiline node 709 b which will return IMSI and its own address asService MSC address. MT-FWD-SM from I-SMSC 1301 is routed to multilinenode 709 b which will submit the message to SMPP Gateway 1305 on homeMDN/MSISDN since Home SMSC 1201 will not honor foreign MDN/MSISDN toterminate SMS. According to some embodiment the Home SMSC 1201 willapply standard call flow to terminate the SMS to the end customer. Forexample, if the customer is at home then SMSReq to CDMA HLR 903 willreturn serving MSC location to which SMS will be terminated else ifcustomer is roaming then SRI-SM DIP would be required towards I-HLR 905.

The IWF-SMSC platform 1301 sends SRI_SM (MSISDN_F) to the multiline hub709 b (message 1311). The hub then relays the message SRI_SM(MSISDN_F)to the GMM 707 (message 1313). The GMM 707 responds withSRI_SM_ACK(IMSI,MSC=Multiline Node) to the hub 709 b (message 1315). Thehub then relays the message to IWF-SMSC and partner GMSC platform 1301(message 1317), which in turn sends MT_FWD_SM message to the GMMplatform 707 with parameters: IMSI, CdPa=multiline, SM-RP-OA=Sender'sMSISDN, SM-RP-UI: RECEIVER'S MSISDN=MSISDN_F& message text. (message1319)

The GMM platform 707 then sends the SMPP_Short_SM(ReceiverMSISDN=MSISDN_H) to the SMPP GW 1303 (message 1321). Then the gateway1303 relays the message to the Home SMSC 1201 (message 1323) which italso relays it back to the SMPP GW 1303 (message 1325), which in turnrelays it to the GMM platform 707 (message 1327). The Home SMCS 1201also sends a message SMSREQ(Receiver MDN=Home CLI) to the CDMA HLR 903(message 1329), which in turn returns back with an SMSRED_ACK message(message 1331). Subsequently the Home SMSC 1201 submits the SM as pointto point SMS_PtoP to V-MSC 1305 (message 1333) which in return sends theSMS_PtoP_ACK (message 1335) and routes the SM normally. Then the HomeSMCS 1201 sends a SMPP_Deliver_SM_Msg ID to the SMPP GW 1303 (message1337) which relays it the GMM platform 707 (message 1339). The GMMplatform 707 responds with SMPP_Deliver_SM_Resp (message 1341), which isrelayed to the Home SMSC 1201 (message 1343). Finally the GMM platform707 also sends the acknowledgement message MT_FWD_SM_ACK to the IWF-SMSCand partner GMSC platform 1303 (message 1345).

FIG. 14 illustrates computing hardware (e.g., computer system) uponwhich an embodiment according to the invention can be implemented. Thecomputer system 1400 includes a bus 1401 or other communicationmechanism for communicating information and a processor 1403 coupled tothe bus 1401 for processing information. The computer system 1400 alsoincludes main memory 1405, such as random access memory (RAM) or otherdynamic storage device, coupled to the bus 1401 for storing informationand instructions to be executed by the processor 1403. Main memory 1405also can be used for storing temporary variables or other intermediateinformation during execution of instructions by the processor 1403. Thecomputer system 1400 may further include a read only memory (ROM) 1407or other static storage device coupled to the bus 1401 for storingstatic information and instructions for the processor 1403. A storagedevice 4109, such as a magnetic disk or optical disk, is coupled to thebus 1401 for persistently storing information and instructions.

The computer system 1400 may be coupled via the bus 1401 to a display1411, such as a cathode ray tube (CRT), liquid crystal display, activematrix display, or plasma display, for displaying information to acomputer user. An input device 1413, such as a keyboard includingalphanumeric and other keys, is coupled to the bus 1401 forcommunicating information and command selections to the processor 1403.Another type of user input device is a cursor control 1415, such as amouse, a trackball, or cursor direction keys, for communicatingdirection information and command selections to the processor 1403 andfor controlling cursor movement on the display 1411.

According to an embodiment of the invention, the processes describedherein are performed by the computer system 1400, in response to theprocessor 1403 executing an arrangement of instructions contained inmain memory 1405. Such instructions can be read into main memory 605from another computer-readable medium, such as the storage device 1409.Execution of the arrangement of instructions contained in main memory1405 causes the processor 1403 to perform the process steps describedherein. One or more processors in a multi-processing arrangement mayalso be employed to execute the instructions contained in main memory1405. In alternative embodiments, hard-wired circuitry may be used inplace of or in combination with software instructions to implement theembodiment of the invention. Thus, embodiments of the invention are notlimited to any specific combination of hardware circuitry and software.

The computer system 1400 also includes a communication interface 1417coupled to bus 1401. The communication interface 1417 provides a two-waydata communication coupling to a network link 1419 connected to a localnetwork 1421. As an example, communication interface 1417 may be a localarea network (LAN) card (e.g. for Ethernet™) to provide a datacommunication connection to a compatible LAN. Wireless links can also beimplemented. In any such implementation, communication interface 1417sends and receives electrical, electromagnetic, or optical signals thatcarry digital data streams representing various types of information.Further, the communication interface 1417 can include peripheralinterface devices, such as a Universal Serial Bus (USB) interface, aPCMCIA (Personal Computer Memory Card International Association)interface, etc. Although a single communication interface 1417 isdepicted in FIG. 14, multiple communication interfaces can also beemployed.

The network link 1419 typically provides data communication through oneor more networks to other data devices. For example, the network link1419 may provide a connection through local network 1421 to a hostcomputer 1423, which has connectivity to a network 1425 (e.g. a widearea network (WAN) or the global packet data communication network nowcommonly referred to as the “Internet”) or to data equipment operated bya service provider. The local network 1421 and the network 1425 both useelectrical, electromagnetic, or optical signals to convey informationand instructions. The signals through the various networks and thesignals on the network link 1419 and through the communication interface1417, which communicate digital data with the computer system 1400, areexemplary forms of carrier waves bearing the information andinstructions.

The computer system 1400 can send messages and receive data, includingprogram code, through the network(s), the network link 1419, and thecommunication interface 1417. In the Internet example, a server (notshown) might transmit requested code belonging to an application programfor implementing an embodiment of the invention through the network1425, the local network 1421 and the communication interface 1417. Theprocessor 1403 may execute the transmitted code while being receivedand/or store the code in the storage device 1409, or other non-volatilestorage for later execution. In this manner, the computer system 1400may obtain application code in the form of a carrier wave.

The term “computer-readable medium” as used herein refers to any mediumthat participates in providing instructions to the processor 1403 forexecution. Such a medium may take many forms, including but not limitedto non-volatile media, volatile media, and transmission media.Non-volatile media include, for example, optical or magnetic disks, suchas the storage device 1409. Volatile media include dynamic memory, suchas main memory 1405. Transmission media include coaxial cables, copperwire and fiber optics, including the wires that comprise the bus 1401.Transmission media can also take the form of acoustic, optical, orelectromagnetic waves, such as those generated during radio frequency(RF) and infrared (IR) data communications. Common forms ofcomputer-readable media include, for example, a floppy disk, a flexibledisk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM,CDRW, DVD, any other optical medium, punch cards, paper tape, opticalmark sheets, any other physical medium with patterns of holes or otheroptically recognizable indicia, a RAM, a PROM, and EPROM, a FLASH-EPROM,any other memory chip or cartridge, a carrier wave, or any other mediumfrom which a computer can read.

Various forms of computer-readable media may be involved in providinginstructions to a processor for execution. For example, the instructionsfor carrying out at least part of the embodiments of the invention mayinitially be borne on a magnetic disk of a remote computer. In such ascenario, the remote computer loads the instructions into main memoryand sends the instructions over a telephone line using a modem. A modemof a local computer system receives the data on the telephone line anduses an infrared transmitter to convert the data to an infrared signaland transmit the infrared signal to a portable computing device, such asa personal digital assistant (PDA) or a laptop. An infrared detector onthe portable computing device receives the information and instructionsborne by the infrared signal and places the data on a bus. The busconveys the data to main memory, from which a processor retrieves andexecutes the instructions. The instructions received by main memory canoptionally be stored on storage device either before or after executionby processor.

While certain exemplary embodiments and implementations have beendescribed herein, other embodiments and modifications will be apparentfrom this description. Accordingly, the invention is not limited to suchembodiments, but rather to the broader scope of the presented claims andvarious obvious modifications and equivalent arrangements.

TABLE 1 GLOSSARY Acronym/ Abbreviation Description CDR Call DetailRecord FPMN Foreign Public Mobile Network (partner network) GMSC GatewayMSC GPRS General Packet Radio Service GT Global Title HLR Home LocationRegister HPMN Home Public Mobile Network IMSI International MobileSubscriber Identity (of HPMN) - MAP Message Application Part - from GSM09.02 GSM Standards MGT Mobile Global Title (derived from IMSI) (E.214)MMS Multimedia Messaging Service MO Mobile Originated MSC MobileSwitching Center MSISDN Mobile Subscriber ISDN Number (phone number)MSISDN_H Home MSISDN of MultiLine Subscriber MSISDN_F Foreign MSISDN ofMultiLine Subscriber MSRN Mobile Station Roaming Number MT MobileTerminated NDC Network Destination Code PRN Provide Roaming Number MAPmessage SCCP Signaling Capabilities and Control Part SG SignalingGateway SIMM-R Single IMSI Multiple MSISDN - Roaming SMS Short MessageService SMSC Short Message Service Center SRI Send Routing InformationMAP message SRGF Signaling Relay Gateway Framework SS7 Signaling System7 USSD Unstructured Supplementary Services Data VLR Visited LocationRegister VMSC Visited Mobile Switching Center MSC_H Serving VMSC in HPMNVMSC-V Serving VMSC in VPMN VPMN Visited Public Mobile Network

What is claimed is:
 1. A method comprising: provisioning a communicationdevice with a plurality of communication access numbers respectivelyassociated with a plurality of communication service regions, whereinthe plurality of communication access numbers are associated with asingle subscriber identity module (SIM) of the communication device;selecting a target communication access number, from among the pluralityof communication access numbers, based on a location of thecommunication device, such that the selected target communication accessnumber is associated with a communication service region, of theplurality of communication service regions, that correspond to thelocation of the communication device; initiating a communicationsession, with a called device, based on the selected targetcommunication access number; and selecting a second communication accessnumber, from among the plurality of communication access numbers,associated with a communication service region, of the plurality ofcommunication service regions, that corresponds to a local communicationaccess number of the called device, the target communication accessnumber and the second communication access number being different fromone another, wherein the initiation of the communication sessionincludes providing the second communication access number to the calleddevice for display at the called device.
 2. The method of claim 1,further comprising: presenting caller identification information,corresponding to the second communication access number, at the calleddevice.
 3. The method of claim 1, wherein the plurality of communicationaccess numbers are concurrently active on the communication device forinitiating or receiving the communication session.
 4. The method ofclaim 1, further comprising: detecting a request to register thecommunication device in a communication network within one of theplurality of communication service regions; and determining the locationof the communication device based on the request, the communicationnetwork, or a combination thereof.
 5. The method of claim 4, furthercomprising: designating one communication access number from among theplurality of communication access numbers as a primary communicationaccess number for the communication device while the device is at thelocation, wherein the one communication access number is associated withthe one of the plurality of communication service regions.
 6. The methodof claim 4, further comprising: in response to the request to registerthe communication device, presenting an option for selecting the targetcommunication access number from among the plurality of communicationaccess numbers.
 7. The method of claim 1, further comprising: updating aroaming profile for the communication device within a communicationinfrastructure based on the target communication access number, whereinthe communication session is relayed to or from the communication devicebased on the roaming profile.
 8. The method of claim 1, wherein theplurality of service regions correspond to a plurality of differentcountries.
 9. An apparatus comprising a processor configured to:provision a communication device with a plurality of communicationaccess numbers respectively associated with a plurality of communicationservice regions, wherein the plurality of communication access numbersare associated with a single subscriber identity module (SIM) of thecommunication device, and the plurality of service regions correspondingto a plurality of different countries; and select a target communicationaccess number, from among the plurality of communication access numbers,based on a location of the communication device, such that the selectedtarget communication access number is associated with a communicationservice region, of the plurality of communication service regions, thatcorrespond to the location of the communication device; initiate acommunication session, with a called device, based on the selectedtarget communication access number; and select a second communicationaccess number, from among the plurality of communication access numbers,associated with a communication service region, of the plurality ofcommunication service regions, that corresponds to a local communicationaccess number of the called device, the target communication accessnumber and the second communication access number being different fromone another, wherein the initiation of the communication sessionincludes providing the second communication access number to the calleddevice for display at the called device.
 10. The apparatus of claim 9,further configured to: present caller identification information,corresponding to the second communication access number, at the calleddevice.
 11. The apparatus of claim 9, wherein the plurality ofcommunication access numbers are concurrently active on thecommunication device for initiating or receiving the communicationsession.
 12. The apparatus of claim 9, further configured to: detect arequest to register the communication device in a communication networkwithin one of the plurality of communication service regions; anddetermine the location of the communication device based on the request,the communication network, or a combination thereof.
 13. The apparatusof claim 12, further configured to: designate one communication accessnumber from among the plurality of communication access numbers as aprimary communication access number for the communication device whilethe device is at the location, wherein the one communication accessnumber is associated with the one of the plurality of communicationservice regions.
 14. The apparatus of claim 12, further configured to:in response to the request to register the communication device, presentan option for selecting the target communication access number fromamong the plurality of communication access numbers.
 15. The apparatusof claim 9, further configured to: update a roaming profile for thecommunication device within a communication infrastructure based on thetarget communication access number, wherein the communication session isrelayed to or from the communication device based on the roamingprofile.
 16. The apparatus of claim 9, wherein the plurality of serviceregions correspond to a plurality of different countries.
 17. A systemcomprising: a communication device configured with a subscriber identitymodule; and a platform configured to: provision the communication devicewith a plurality of communication access numbers respectively associatedwith a plurality of communication service regions, wherein the pluralityof communication access numbers are associated with the subscriberidentity module SIM); select a target communication access number, fromamong the plurality of communication access numbers, based on a locationof the communication device, such that the selected target communicationaccess number is associated with a communication service region, of theplurality of communication service regions, that correspond to thelocation of the communication device; initiate a communication session,with a called device, based on the selected target communication accessnumber; and select a second communication access number, from among theplurality of communication access numbers, associated with acommunication service region, of the plurality of communication serviceregions, that corresponds to a local communication access number of thecalled device, the target communication access number and the secondcommunication access number being different from one another, whereinthe initiation of the communication session includes providing thesecond communication access number to the called device for display atthe called device.
 18. The system of claim 17, wherein the platform isfurther configured to: present caller identification, corresponding tothe second communication access number, at the called device.
 19. Thesystem of claim 17, wherein the plurality of communication accessnumbers are concurrently active on the communication device forinitiating or receiving the communication session.
 20. The system ofclaim 17, wherein the plurality of service regions correspond to aplurality of different countries.